Document Bundler checksum behavior for default gems - #9735
Merged
Conversation
Signed-off-by: Patrick Linnane <patrick@linnane.io>
hsbt
enabled auto-merge
July 29, 2026 04:43
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was the end-user or developer problem that led to this PR?
Bundler's own checksum is only included when the matching
.gemfile is cached. Bundler installed as a default gem may not have this file, but this behavior was not documented.What is your fix for the problem, implemented in this PR?
Document the limitation under
lockfile_checksumsand regeneratebundle-config(1). This does not change runtime behavior.@Edouard-chin, you mentioned in #9512 that you would be happy to review this, so here it is 😄
Make sure the following tasks are checked